Checked it out real quick and it looks fine, although it is indeed a bit hard to test. Maybe you can think of a debug console command or two to help it out, or some sort of seed examiner item?

It would also help if the UI had a bit more of an indication of what it does. Rather than 4 boxes in a row try to add some minimal decoration so maybe it ends up looking like:

[] + [] -> [][]

I added a command heldGenomeCheck which returns the genes of the held item. The problem with testing this would be that seeds will almost always have the default gene, unless somehow we are able to randomize the starting genes (while spawning) from a list of possible values. But to test this, in the scope of this PR, you can increase the mutation value to something ridiculous like 0.5 and get different gene values.

@xrtariq2594 mind doing a bit of general testing for SimpleFarming then merge this? I can confirm the seed mixer works, but didn't test anything in general (like if seeds with or without mixing actually grow, etc)

I spoke with @arpan98 and he came up with a general testing guide for this PR. Thought it might be helpful if I sent it here.

1. give seedmixer 1, place it, fiddle with it.
2. try give blueberryseed, should give you a blueberry seed with genome F (default). You can use the command heldGenomeCheck to check genome of held item.
3. Drag blueberries onto the input slots of the seedmixer- only seeds should be able to be dropped on the slots.
4. Check genome of input and output seeds. If you want, you can fiddle around with the mutation constant in the GenomeSystem to see what works best (I just put in a random value for now).
5. Try growing the seeds, checking genome of resultant blueberry.

Maybe add a second variant of the blueberry with a different genome? Would make testing a lot easier (won't have to wait for random mutations to see genome changes).

Hey, so because of the recent refactor to this module, I think we might need to rework this whole PR. Adding more commits onto this PR will just make it messy, so I think we should close this one and create a new one. We should still be able to salvage large portions of the code.

Pinging @arpan98 @Cervator

I also think that the Hunger stuff isn't the feature we would want to add first, as it involves adding a dependency to Hunger, which we may or may not want to do (ping @jellysnake. Maybe we should move part of this to EdibleFlora?). I would say we should start off with things like flower/bush color or something simple with two possible varieties (one dominant, one recessive).

Sorry for coming back to this only now 🙈 I'm closing this due to date and conflicts.